Integration of radio and core layers

ABSTRACT

A method, a device, and a non-transitory storage medium are described in which a radio and core integrated layers service is provided. The service provides a direct mapping of a quality of service flow between a packet data unit layer and a service data adaptation layer associated with a user plane function and a central unit-user plane function without an intermediary mapping of a tunneling protocol in the user plane.

BACKGROUND

Development and design of radio access networks (RAN) and core networkspresent certain challenges from a network-side perspective and an enddevice perspective. For example, depending on the configurations fromboth network-side and end device-side perspectives, such configurationsmay reduce the effective use of resources and negatively impact variousperformance metrics, such as latency, etc. Accordingly, a need exists toovercome these challenges.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an exemplary environment in which anexemplary embodiment of a radio and core integrated layers service maybe implemented;

FIG. 2A is a diagrams illustrating an exemplary process in which anexemplary embodiment of the radio and core integrated layers service maybe implemented;

FIG. 2B is a diagram of an exemplary embodiment of an edge user planenetwork device of FIG. 2A;

FIG. 3 is a messaging diagram illustrating an exemplary process of anexemplary embodiment of the radio and core integrated layers service;

FIG. 4 is a diagram illustrating exemplary components of a device thatmay correspond to one or more of the devices illustrated and describedherein; and

FIG. 5 is a flow diagram illustrating an exemplary process of anexemplary embodiment of the radio and core integrated layers service.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. Also, the following detailed description does notlimit the invention.

A next generation or future wireless network should support various usecases, meet various performance metrics, allow for scalability andflexibility, and so forth. As a part of next generation or futuregeneration wireless network services, quality of service (QoS) rules andpolicies may be mapped to user plane (UP) packets of QoS flows betweenan end device and a user plane function (UPF). In the context of a splitwireless network architecture, a central unit-user plane (CU-UP)function may map a QoS flow and a data radio bearer, and mark a QoS flowidentifier (QFI) for both uplink and downlink packets. A protocol entityof Service Data Adaptation Protocol (SDAP) may be configured for eachindividual packet data unit (PDU) session. Also, a General Packet RadioService Tunneling Protocol User Plane (GTP-U) tunnel, which carries theQoS flow, has to be mapped. For example, the UPF may map a QoS flow intothe GTP-U tunnel and then the CU-UP may map the QoS flow from the GTP-Utunnel to the data radio bearer. However, this framework can result inunnecessary use of network resources and negatively impact QoS metrics,such as latency.

According to exemplary embodiments, a radio and core integrated layersservice is described. According to an exemplary embodiment, a user planenetwork device may provide the radio and core integrated layers service.According to an exemplary embodiment, the user plane network deviceincludes logic that maps QoS flows into radio bearers with nointermediary mapping into GTP-U tunnels. According to an exemplaryembodiment, the user plane network device includes PDU, SDAP, and PacketData Convergence Protocol (PDCP) functions. According to an exemplaryembodiment, the user plane network device may determine whether toinvoke the radio and core integrated layers service or not based oncollocation guidance information. According to an exemplary embodiment,when the radio and core integrated layers service is not invoked, a QoSflow mapped to a PDU session may be mapped to a GTP-U tunnel, asdescribed herein.

As a result, the radio and core integrated layers service may improvenetwork resource utilization in a network. For example, use of variousnetwork resources (e.g., physical, logical, virtual, radio) that stemfrom QoS flow mapping in relation to network devices of a RAN or networkdevices of the RAN and a core network may be reduced. Additionally, theradio and core integrated layers service may improve quality of servicemetrics for end device applications and services based on theelimination of GTP-U tunnel mapping.

FIG. 1 is a diagram illustrating an exemplary environment 100 in whichan exemplary embodiment of the radio and core integrated layers servicemay be implemented. As illustrated, environment 100 includes an accessnetwork 105 and a core network 150. Access network 105 includes accessdevices 110, and core network 150 includes core devices 155. Environment100 further includes an end device 180.

The number, the type, and the arrangement of network devices in accessnetwork 105 and core network 150, as illustrated and described, areexemplary. The number of end devices 180 is exemplary. A network device,a network element, or a network function (referred to herein simply as anetwork device) may be implemented according to one or multiple networkarchitectures (e.g., a client device, a server device, a peer device, aproxy device, a cloud device, a virtualized function, and/or anothertype of network architecture (e.g., Software Defined Network (SDN),virtual, logical, network slicing, etc.). Additionally, a network devicemay be implemented according to various computing architectures, such ascentralized, distributed, cloud (e.g., elastic, public, private, etc.),edge, fog, and/or another type of computing architecture.

Environment 100 includes communication links between the networkdevices, and between end device 180 and network devices. Environment 100may be implemented to include wired, optical, and/or wirelesscommunication links among the network devices and the networksillustrated. A communicative connection via a communication link may bedirect or indirect. For example, an indirect communicative connectionmay involve an intermediary device and/or an intermediary network notillustrated in FIG. 1. A direct communicative connection may not involvean intermediary device and/or an intermediary network. The number andthe arrangement of communication links illustrated in environment 100are exemplary.

Environment 100 may include various planes of communication including,for example, a control plane, a user plane, and a network managementplane. Environment 100 may include other types of planes ofcommunication. A message communicated in support of the radio and coreintegrated layers service may use at least one of these planes ofcommunication. Additionally, an interface of a network device (e.g.,relative to an interface defined by a standards body, such as ThirdGeneration Partnership Project (3GPP), International TelecommunicationUnion (ITU), European Telecommunications Standards Institute (ETSI),etc.) may be modified in order to support the communication (e.g.,transmission and reception of messages, information elements (IE),attribute value pairs (AVPs), etc.) between network devices and supportof the radio and core integrated layers service, as described herein.According to various exemplary implementations, the interface may be aservice-based interface or a reference point-based interface.

Access network 105 may include one or multiple networks of multipletypes and technologies. For example, access network 105 may include aFourth Generation (4G) RAN, a 4.5G RAN, a Fifth Generation (5G) RAN,and/or another type of future generation RAN. By way of further example,access network 105 may be implemented to include an Evolved UMTSTerrestrial Radio Access Network (E-UTRAN) of a Long Term Evolution(LTE) network, an LTE-Advanced (LTE-A) network, and/or an LTE-A Pronetwork, and a next generation (NG) RAN. Access network 105 may furtherinclude other types of wireless networks, such as a WiFi network, aWorldwide Interoperability for Microwave Access (WiMAX) network, a localarea network (LAN), or another type of network (e.g., a legacy ThirdGeneration (3G) RAN, etc.) that may provide an on-ramp to access devices110 and/or core network 150.

According to various exemplary embodiments, access network 105 may beimplemented to include various architectures of wireless service, suchas, for example, macrocell, microcell, femtocell, picocell, metrocell,NR cell, LTE cell, non-cell, or another type of cell architecture.Additionally, according to various exemplary embodiments, access network105 may be implemented according to various wireless technologies (e.g.,radio access technologies (RATs), etc.), wireless standards, wirelessfrequencies/bands/carriers, licensed radio spectrum, unlicensed radiospectrum, and/or other attributes of radio communication.

Access network 105 may include different and multiple functionalsplitting, such as options 1, 2, 3, 4, 5, 6, 7, or 8 that relate tocombinations of access network 105 and core network 150 including anEvolved Packet Core (EPC) network and/or a NG core (NGC) network, or thesplitting of the various layers (e.g., physical layer, Media AccessControl (MAC) layer, Radio Link Control (RLC) layer, and PDCP layer),plane splitting (e.g., user plane, control plane, etc.), CU anddistributed unit (DU), interface splitting (e.g., F1-U, F1-C, E1, Xn-C,Xn-U, X2-C, Common Public Radio Interface (CPRI), etc.) as well as othertypes of network services, such as dual connectivity (DC) or higher(e.g., a secondary cell group (SCG) split bearer service, a master cellgroup (MCG) split bearer, an SCG bearer service, non-standalone (NSA),standalone (SA), etc.), CA (e.g., intra-band, inter-band, contiguous,non-contiguous, etc.), network slicing, coordinated multipoint (CoMP),various duplex schemes (e.g., frequency division duplex (FDD), timedivision duplex (TDD), half-duplex FDD (H-FDD), etc.), and/or anothertype of connectivity service.

Depending on the implementation, access network 105 may include one ormultiple types of network devices, such as access devices 110. Forexample, access devices 110 may include an eNB, a gNB, an evolved LongTerm Evolution (eLTE) eNB, a radio network controller (RNC), a remoteradio head (RRH), a baseband unit (BBU), a small cell node (e.g., apicocell device, a femtocell device, a microcell device, a home eNB, arepeater, etc.)), or another type of wireless node. According to anexemplary embodiment, access device 110 includes logic that provides theradio and core integrated layers service, as described herein.

Core network 150 may include multiple networks of multiple types andtechnologies. According to an exemplary embodiment, core network 150includes a complementary network of access network 105. For example,core network 150 may be implemented to include a core network of an LTE,LTE-A network, and/or an LTE-A Pro network, a next generation core (NGC)network and/or another type future generation core network. Core network150 may include a legacy core network.

Depending on the implementation, core network 150 may include varioustypes of network devices, such as core devices 155. For example, coredevices 155 may include a packet gateway (PGW), a serving gateway (SGW),a home subscriber server (HSS), an authentication, authorization, andaccounting (AAA) server, a policy charging and rules function (PCRF), acharging system (CS), a user plane function (UPF), an access andmobility management function (AMF), a mobility management entity (MME),a session management function (SMF), a unified data management (UDM)device, an authentication server function (AUSF), a network sliceselection function (NSSF), a network repository function (NRF), a policycontrol function (PCF), a network exposure function (NEF), and/or anapplication function (AF). According to other exemplary implementations,core devices 155 may include additional, different, and/or fewer networkdevices than those described. For example, core devices 155 may includea non-standard and/or proprietary network device. According to anexemplary embodiment, core device 155 includes logic that provides theradio and core integrated layers service, as described herein.

End device 180 includes a device that has computational and wirelesscommunication capabilities. Depending on the implementation, end device180 may be a mobile device, a portable device, a stationary device, adevice operated by a user, or a device not operated by a user. Forexample, end device 180 may be implemented as a Mobile Broadband device,a Machine Type Communication (MTC) device, an Internet of Things (IoT)device, an enhanced MTC device (eMTC) (also known as Cat-M1), aNarrowBand IoT (NB-IoT) device, a machine-to-machine (M2M) device, auser device, or other types of wireless end nodes. By way of furtherexample, end device 180 may be implemented as a smartphone, a personaldigital assistant, a tablet, a netbook, a phablet, a wearable device(e.g., a watch, glasses, etc.), a set top box, an infotainment system ina vehicle, a vehicle support system, a smart television, a game system,a music playing system, or other types of wireless end devices. Enddevice 180 may be configured to execute various types of software (e.g.,applications, programs, etc.). The number and the types of software mayvary among end devices 180.

End device 180 may support one or multiple RATs (e.g., 4G, 5G, etc.) andvarious portions of the radio spectrum (e.g., multiple frequency bands,multiple carrier frequencies, licensed, unlicensed, etc.), networkslicing, DC service, and/or other types of connectivity services.Additionally, end device 180 may include one or multiple communicationinterfaces that provide one or multiple (e.g., simultaneous) connectionsvia the same or different RATs, frequency bands, carriers, networkslices, and so forth. The multimode capabilities of end device 180 mayvary among end devices 180.

FIG. 2A is a diagram illustrating an exemplary environment 200 in whichan exemplary embodiment of the radio and core integrated layers servicemay be implemented. As illustrated, environment 200 includes accessdevice 110 and core device 155, such as edge user plane network device205, a CU-UP 220 and an SMF 225. Edge user plane network device 205includes a UPF 210 and a CU-UP 215. Environment 200 further includesinterfaces N3, N4, N6, and F1-U, as well as a data network 230. In 4Gnetworks, GTP-U tunnels and radio bearers have a 1:1 mapping, whereas 5Gnetworks allow for the mapping of QoS flows to GTP-U tunnels to radiobearers.

Referring to FIG. 2B, UPF 210 includes a PDU layer 250, and CU-UP 215includes an SDAP layer 255 and a PDCP layer 260. Although notillustrated, UPF 210 and CU-UP 215 include other logic or layers of aprotocol stack for the user plane. For example, UPF 210 may include alayer 1, a layer 2, a user datagram (UDP)/Internet Protocol (IP) layer,a UP encapsulation layer, and/or other user plane logic. Additionally,for example, depending on the split option, CU-UP 215 may include aradio link control (RLC) layer, a radio resource control (RRC) layer,and/or other user plane logic. As further illustrated, edge user planenetwork device 205 may include a manager 270. Manager 270 may includelogic that determines whether QoS mapping for a PDU session includes oromits GTP-U mapping based on collocation guidance information, asdescribed herein.

As previously described in relation to environment 100, the number ofnetwork devices, the type of network devices, the communication links,and so forth, in environment 200 are exemplary.

Referring back to FIG. 2A, according to an exemplary embodiment, UPF 210and CU-UP 215 of edge user plane network device 205 may map QoS flows235 from PDU layer 250 to radio bearers via SDAP 255 and PDCP 260without GTP-U tunnel mapping. In contrast, according to an exemplaryembodiment, UPF 210 of edge user plane network device 205 and CU-UP 220may map QoS flows from PDU layer 250 to radio bearers with GTP-U tunnelmapping. For example, CU-UP 220 may include GTP-U as a part of itsprotocol stack, along with other layers (e.g., L1, L2, UDP/IP, etc.). Asdescribed herein, edge user plane network device 205 may include logicto determine whether a QoS flow is mapped with or without GTP-Utunneling based on collocation guidance information. Edge user planenetwork device 205 may transmit the mapped uplink user plane data of QoSflows 235 and 240 via the N6 interface to data network 230. On the otherhand, edge user plane network device 205 may transmit the mappeddownlink user plane data of QoS flows 235 via the F1-U to a distributedunit-user plane (DU-UP) function (not illustrated), and the mappeddownlink user plane data of QoS flows 240 via the N3 interface to CU-UP220. CU-UP 220 may map QoS flows 240 to GTP-U and a radio bearer.

FIG. 3 is a diagram illustrating an exemplary process 300 of anexemplary embodiment of the radio and core integrated layers service.For example, the messaging diagram relates to an exemplary scenario inwhich a PDU session is created for end device 180. The messagesillustrated and described are exemplary. Additionally, some messagesthat may be used to establish a PDU session have been omitted for thesake of brevity.

Referring to FIG. 3, in response to receiving a PDU SessionEstablishment Request from end device 180 (not illustrated), an AMF 305may generate and transmit a PDU Session Create Context Request message320. For example, an Nsmf_PDUSession_CreateSMContext Request message mayinclude a Subscription Permanent Identifier (SUPI), Data Network Name(DNN), Single-Network Slice Selection Assistance information(S-NSSAI(s)), a PDU Session Identifier, an AMF identifier, a RequestType, User location information, and other information of such messagein accordance with a 3GPP or other governing body standard.

In response to receiving PDU Session Create Context Request message 320,SMF 225 may select edge user plane network device 205 as the UPF basedon user location information, DNN information 325 (and other informationincluded in PDU Session Create Context Request message 320). SMF 225 maygenerate and transmit a message 330, which includes information relatingto resource allocation for the PDU session, to edge user plane networkdevice 205. For example, message 330 may include collocation guidanceinformation. The collocation guidance information may indicate the UPFfunction of edge user plane network device 205 is to be used in supportof the PDU session to be created. Additionally, or alternatively, forexample, the collocation guidance information may indicate that directmapping between the PDU layer and the SDAP layer is to be used (e.g.,QoS flows 235 of FIG. 2A). According to an exemplary embodiment, SMF 225may make this determination based on the type of end device applicationfor which the PDU session is being established. Additionally, oralternatively, SMF 225 may make this determination based on otherfactors, such as network congestion level at a CU-UP and/or othernetwork device of the RAN or core network, subscription informationpertaining to end device 180, or other types of context information.Still further, SMF 225 may make this determination based on policiesreceived from a PCF (not illustrated). For example, the polices mayrelate to a service level agreement (SLA) for the flow, for a networkslice or service, and SMF 225 may use this information as a basis toinclude the collocation guidance in the N4 message. Alternatively, SMF225 may store and/or use static rules as a basis to determine whether toinclude collocation guidance information. According to still otherexemplary embodiments, SMF 225 may communicate with an NRF (notillustrated) during node selection, and such communication may includeinformation that forms a basis for determining the inclusion or omissionof collocation guidance information.

As further illustrated, SMF 225 may generate and transmit aNamf_Communication_N1N2 Message Transfer Response, to AMF 305. Message335 may include a PDU Session Identifier, N2 SM Information (QoSProfile, core network (CN) Tunnel information, S-NSSAI from the AllowedNSSAI, PDU Session Type, and other information of such message inaccordance with a 3GPP or other governing body standard. Additionally,as illustrated, message 335 may include the collocation guidanceinformation. AMF 305 generates and transmits a message 340 to CU-CP 315.For example, an N2 PDU Session Request message, which may include N2session management (SM) information, a PDU Session identifier, and an N1SM container (PDU Session Establishment Accept). The N2 PDU SessionRequest message may include the collocation guidance information.

In response to receiving message 340, CU-CP 315 may select the CU-UP ofedge user plane network device 205 based on the collocation guidance andCN tunnel information 345. Based on this selection, CU-CP 315 maygenerate and transmit a message 350, which includes information relatingto resource allocation for the PDU session, to edge user plane networkdevice 205. For example, message 350 may include collocation guidanceinformation. The collocation guidance information may indicate the CU-UPfunction of edge user plane network device 205 is to be used in supportof the PDU session to be created. Additionally, or alternatively, forexample, the collocation guidance information may indicate that directmapping between the PDU layer and the SDAP layer is to be used (e.g.,QoS flows 235 of FIG. 2A). In response to receiving message 350, edgeuser plane network device 205 provides the radio and core integratedlayers service based on the collocation guidance information for UPF andCU-UP functions 355. For example, according to this exemplary scenario,edge user plane network device 205 may provide QoS mapping without GTP-U(e.g., QoS flow 235 of FIG. 2A) based on a direct plug-in of PDU andSDAP layers for uplink and downlink data in the user plane.

FIG. 3 illustrates an exemplary process of the radio and core integratedlayers service, however, according to other exemplary embodiments, theprocess may include additional, different, and/or fewer steps, and/orinclude additional, different, and/or fewer messages. For example,according to another exemplary scenario, edge user plane network device205 may provide QoS mapping with GTP-U based on the collocation guidanceinformation for UPF and CU-UP functions.

FIG. 4 is a diagram illustrating exemplary components of a device 400that may be included in one or more of the devices described herein. Forexample, device 400 may correspond to components included in accessdevices 110, core devices 155, end device 180, edge user plane networkdevice 205, UPF 210, CU-UP 215 and/or other devices described herein. Asillustrated in FIG. 4, device 400 includes a bus 405, a processor 410, amemory/storage 415 that stores software 420, a communication interface425, an input 430, and an output 435. According to other embodiments,device 400 may include fewer components, additional components,different components, and/or a different arrangement of components thanthose illustrated in FIG. 4 and described herein.

Bus 405 includes a path that permits communication among the componentsof device 400. For example, bus 405 may include a system bus, an addressbus, a data bus, and/or a control bus. Bus 405 may also include busdrivers, bus arbiters, bus interfaces, clocks, and so forth.

Processor 410 includes one or multiple processors, microprocessors, dataprocessors, co-processors, application specific integrated circuits(ASICs), controllers, programmable logic devices, chipsets,field-programmable gate arrays (FPGAs), application specificinstruction-set processors (ASIPs), system-on-chips (SoCs), centralprocessing units (CPUs) (e.g., one or multiple cores), microcontrollers,and/or some other type of component that interprets and/or executesinstructions and/or data. Processor 410 may be implemented as hardware(e.g., a microprocessor, etc.), a combination of hardware and software(e.g., a SoC, an ASIC, etc.), may include one or multiple memories(e.g., cache, etc.), etc.

Processor 410 may control the overall operation or a portion ofoperation(s) performed by device 400. Processor 410 may perform one ormultiple operations based on an operating system and/or variousapplications or computer programs (e.g., software 420). Processor 410may access instructions from memory/storage 415, from other componentsof device 400, and/or from a source external to device 400 (e.g., anetwork, another device, etc.). Processor 410 may perform an operationand/or a process based on various techniques including, for example,multithreading, parallel processing, pipelining, interleaving, etc.

Memory/storage 415 includes one or multiple memories and/or one ormultiple other types of storage mediums. For example, memory/storage 415may include one or multiple types of memories, such as, a random accessmemory (RAM), a dynamic random access memory (DRAM), a static randomaccess memory (SRAM), a cache, a read only memory (ROM), a programmableread only memory (PROM), an erasable PROM (EPROM), an electrically EPROM(EEPROM), a single in-line memory module (SIMM), a dual in-line memorymodule (DIMM), a flash memory (e.g., 2D, 3D, NOR, NAND, etc.), a solidstate memory, and/or some other type of memory. Memory/storage 415 mayinclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid state disk, etc.), a Micro-ElectromechanicalSystem (MEMS)-based storage medium, and/or a nanotechnology-basedstorage medium. Memory/storage 415 may include drives for reading fromand writing to the storage medium.

Memory/storage 415 may be external to and/or removable from device 400,such as, for example, a Universal Serial Bus (USB) memory stick, adongle, a hard disk, mass storage, off-line storage, or some other typeof storing medium (e.g., a compact disk (CD), a digital versatile disk(DVD), a Blu-Ray disk (BD), etc.). Memory/storage 415 may store data,software, and/or instructions related to the operation of device 400.

Software 420 includes an application or a program that provides afunction and/or a process. As an example, with respect to access device110 (e.g., gNB 207, etc.), software 420 may include an application that,when executed by processor 410, provides a function of the radio andcore integrated layers service, as described herein. Software 420 mayalso include firmware, middleware, microcode, hardware descriptionlanguage (HDL), and/or other form of instruction. Software 420 may alsobe virtualized. Software 420 may further include an operating system(OS) (e.g., Windows, Linux, Android, proprietary, etc.).

Communication interface 425 permits device 400 to communicate with otherdevices, networks, systems, and/or the like. Communication interface 425includes one or multiple wireless interfaces and/or wired interfaces.For example, communication interface 425 may include one or multipletransmitters and receivers, or transceivers. Communication interface 425may operate according to a protocol stack and a communication standard.Communication interface 425 may include an antenna. Communicationinterface 425 may include various processing logic or circuitry (e.g.,multiplexing/de-multiplexing, filtering, amplifying, converting, errorcorrection, application programming interface (API), etc.).Communication interface 425 may be implemented as a point-to-pointinterface, a service based interface, etc.

Input 430 permits an input into device 400. For example, input 430 mayinclude a keyboard, a mouse, a display, a touchscreen, a touchlessscreen, a button, a switch, an input port, speech recognition logic,and/or some other type of visual, auditory, tactile, etc., inputcomponent. Output 435 permits an output from device 400. For example,output 435 may include a speaker, a display, a touchscreen, a touchlessscreen, a light, an output port, and/or some other type of visual,auditory, tactile, etc., output component.

As previously described, a network device may be implemented accordingto various computing architectures (e.g., in a cloud, etc.) andaccording to various network architectures (e.g., a virtualizedfunction, etc.). Device 400 may be implemented in the same manner. Forexample, device 400 may be instantiated, created, deleted, or some otheroperational state during its life-cycle (e.g., refreshed, paused,suspended, rebooting, or another type of state or status), usingwell-known virtualization technologies (e.g., hypervisor, containerengine, virtual container, virtual machine, etc.) in a public/privatecloud or other type of network.

Device 400 may perform a process and/or a function, as described herein,in response to processor 410 executing software 420 stored bymemory/storage 415. By way of example, instructions may be read intomemory/storage 415 from another memory/storage 415 (not shown) or readfrom another device (not shown) via communication interface 425. Theinstructions stored by memory/storage 415 cause processor 410 to performa process described herein. Alternatively, for example, according toother implementations, device 400 performs a process and/or a function,as described herein, based on the execution of hardware (processor 410,etc.).

FIG. 5 is a flow diagram illustrating an exemplary process 500 of anexemplary embodiment of the radio and core integrated layers service.According to an exemplary embodiment, edge user plane network device 205(or a component thereof, such as manager 270) may perform a step ofprocess 500. Additionally, for example, processor 410 may executesoftware 420 to perform a step illustrated in FIG. 5 and describedherein. Additionally, or alternatively, a step illustrated in FIG. 5 maybe performed by execution of only hardware.

In block 505, a message from an SMF is received. Edge user plane networkdevice 205 may receive a message pertaining to an establishment of a PDUsession for end device 180. For example, the message may include aresource allocation message.

In block 510, it may be determined whether collocation guidanceinformation is included in the message. For example, edge user planenetwork device 205 may read and analyze the message to determine whetherthe collocation guidance information is included in the message.

When it is determined that the collocation guidance information is notincluded in the message (block 510—NO), an external CU-UP is selected(block 515). For example, edge user plane network device 205 may omit touse an internal CU-UP, and select an external CU-UP (e.g., CU-UP 220)for the PDU session. Edge user plane network device 205 may also selecta UPF function that interfaces with the external CU-UP via an N3interface.

In block 520, a QoS flow of a PDU session may be mapped to a GTP-Utunnel. For example, based on the selection of the external CU-UP, andsubsequent to the establishment of the PDU session, UPF 210 may map aQoS flow of the PDU session to the GTP-U tunnel in the downlink and/ormap the GTP-U tunnel to the PDU session in the uplink.

When it is determined that the collocation guidance information isincluded in the message (block 515—YES), an internal CU-UP is selected(block 525). For example, edge user plane network device 205 may selectto use an internal CU-UP (e.g., CU-UP 215) for the PDU session. Edgeuser plane network device 205 may also select a UPF function thatinterfaces directly with SDAP layer 255 of CU-UP 215.

In block 530, a QoS flow of a PDU session may be mapped to a radiobearer. For example, based on the selection of the internal CU-UP, andsubsequent to the establishment of the PDU session, UPF 210 may map aQoS flow of the PDU session to the radio bearer in the downlink and/ormap the radio bearer to the PDU session in the uplink. As previouslydescribed, intermediary GTP-U mapping may be omitted.

FIG. 5 illustrates an exemplary process 500 of the radio and coreintegrated layers service, however, according to other embodiments,process 500 may include additional operations, fewer operations, and/ordifferent operations than those illustrated in FIG. 5, and describedherein. For example, edge user plane network device 205 may select anexternal CU-UP or an internal CU-UP in response to receiving a message,which may include or not include the collocation guidance information,from a CU-CP, as previously described.

As set forth in this description and illustrated by the drawings,reference is made to “an exemplary embodiment,” “an embodiment,”“embodiments,” etc., which may include a particular feature, structureor characteristic in connection with an embodiment(s). However, the useof the phrase or term “an embodiment,” “embodiments,” etc., in variousplaces in the specification does not necessarily refer to allembodiments described, nor does it necessarily refer to the sameembodiment, nor are separate or alternative embodiments necessarilymutually exclusive of other embodiment(s). The same applies to the term“implementation,” “implementations,” etc.

The foregoing description of embodiments provides illustration, but isnot intended to be exhaustive or to limit the embodiments to the preciseform disclosed. Accordingly, modifications to the embodiments describedherein may be possible. For example, various modifications and changesmay be made thereto, and additional embodiments may be implemented,without departing from the broader scope of the invention as set forthin the claims that follow. The description and drawings are accordinglyto be regarded as illustrative rather than restrictive.

The terms “a,” “an,” and “the” are intended to be interpreted to includeone or more items. Further, the phrase “based on” is intended to beinterpreted as “based, at least in part, on,” unless explicitly statedotherwise. The term “and/or” is intended to be interpreted to includeany and all combinations of one or more of the associated items. Theword “exemplary” is used herein to mean “serving as an example.” Anyembodiment or implementation described as “exemplary” is not necessarilyto be construed as preferred or advantageous over other embodiments orimplementations.

In addition, while a series of blocks has been described with regard toa process illustrated in FIG. 5, the order of the blocks may be modifiedaccording to other embodiments. Further, non-dependent blocks may beperformed in parallel. Additionally, other processes described in thisdescription may be modified and/or non-dependent operations may beperformed in parallel.

Embodiments described herein may be implemented in many different formsof software executed by hardware. For example, a process or a functionmay be implemented as “logic,” a “component,” or an “element.” Thelogic, the component, or the element, may include, for example, hardware(e.g., processor 410, etc.), or a combination of hardware and software(e.g., software 420).

Embodiments have been described without reference to the specificsoftware code because the software code can be designed to implement theembodiments based on the description herein and commercially availablesoftware design environments and/or languages. For example, varioustypes of programming languages including, for example, a compiledlanguage, an interpreted language, a declarative language, or aprocedural language may be implemented.

Use of ordinal terms such as “first,” “second,” “third,” etc., in theclaims to modify a claim element does not by itself connote anypriority, precedence, or order of one claim element over another, thetemporal order in which acts of a method are performed, the temporalorder in which instructions executed by a device are performed, etc.,but are used merely as labels to distinguish one claim element having acertain name from another element having a same name (but for use of theordinal term) to distinguish the claim elements.

Additionally, embodiments described herein may be implemented as anon-transitory computer-readable storage medium that stores data and/orinformation, such as instructions, program code, a data structure, aprogram module, an application, a script, or other known or conventionalform suitable for use in a computing environment. The program code,instructions, application, etc., is readable and executable by aprocessor (e.g., processor 410) of a device. A non-transitory storagemedium includes one or more of the storage mediums described in relationto memory/storage 415.

To the extent the aforementioned embodiments collect, store or employpersonal information of individuals, it should be understood that suchinformation shall be collected, stored, and used in accordance with allapplicable laws concerning protection of personal information.Additionally, the collection, storage and use of such information can besubject to consent of the individual to such activity, for example,through well known “opt-in” or “opt-out” processes as can be appropriatefor the situation and type of information. Collection, storage, and useof personal information can be in an appropriately secure mannerreflective of the type of information, for example, through variousencryption and anonymization techniques for particularly sensitiveinformation.

No element, act, or instruction set forth in this description should beconstrued as critical or essential to the embodiments described hereinunless explicitly indicated as such.

All structural and functional equivalents to the elements of the variousaspects set forth in this disclosure that are known or later come to beknown to those of ordinary skill in the art are expressly incorporatedherein by reference and are intended to be encompassed by the claims. Noclaim element of a claim is to be interpreted under 35 U.S.C. § 112(f)unless the claim element expressly includes the phrase “means for” or“step for.”

What is claimed is:
 1. A method comprising: receiving, by a networkdevice, a message pertaining to an establishment of packet data unit(PDU) session for an end device, wherein the message includes a firstmessage from a session management function and a second message from acentral unit-control plane function; determining, by the network device,that the message includes collocation guidance information; selecting,by the network device in response to the determining, a user planefunction and a central unit-user plane function of the network device;and mapping, by the user plane function and the central unit-user planefunction, a quality of service flow to the PDU session directly with aradio bearer without an intermediary mapping of a General Packet RadioService Tunneling Protocol User Plane (GTP-U) tunnel, wherein thequality of service flow includes at least one of uplink or downlink userplane data.
 2. The method of claim 1, wherein the network device is of afifth generation wireless network.
 3. The method of claim 1, wherein thefirst message includes data indicating a selection of the user planefunction and the second message includes data indicating a selection ofthe central unit-user plane function.
 4. The method of claim 1, whereinthe mapping comprises mapping the quality of service flow between a PDUlayer and a Service Data Adaptation Protocol (SDAP) layer.
 5. The methodof claim 4, wherein the collocation guidance information indicates touse direct mapping between the PDU layer and the SDAP layer.
 6. Themethod of claim 1, further comprising: transmitting, by the networkdevice subsequent to the mapping, downlink user plane data of thequality of service flow to a distributed unit-user plane function via anF1-U interface.
 7. The method of claim 1, further comprising:transmitting, by the network device subsequent to the mapping, uplinkuser plane data of the quality of service flow to a data network via anN6 interface.
 8. A network device comprising: a communication interface;a memory, wherein the memory stores instructions; and a processor,wherein the processor executes the instructions to: receive, via thecommunication interface, a message pertaining to an establishment ofpacket data unit (PDU) session for an end device, wherein the messageincludes a first message from a session management function and a secondmessage from a central unit-control plane function; determine that themessage includes collocation guidance information; select, in responseto the determination, a user plane function and a central unit-userplane function of the network device; and map, by the user planefunction and the central unit-user plane function, a quality of serviceflow to the PDU session directly with a radio bearer without anintermediary mapping of a General Packet Radio Service TunnelingProtocol User Plane (GTP-U) tunnel, wherein the quality of service flowincludes at least one of uplink or downlink user plane data.
 9. Thenetwork device of claim 8, wherein the network device is of a fifthgeneration wireless network.
 10. The network device of claim 8, whereinthe first message includes data indicating a selection of the user planefunction and the second message includes data indicating a selection ofthe central unit-user plane function.
 11. The network device of claim 8,wherein the mapping comprises mapping the quality of service flowbetween a PDU layer and a Service Data Adaptation Protocol (SDAP) layer.12. The network device of claim 11, wherein the collocation guidanceinformation indicates to use direct mapping between the PDU layer andthe SDAP layer.
 13. The network device of claim 8, wherein the processorfurther executes the instructions to: transmit, via the communicationinterface subsequent to the mapping, downlink user plane data of thequality of service flow to a distributed unit-user plane function via anF1-U interface.
 14. The network device of claim 8, wherein the processorfurther executes the instructions to: transmit, via the communicationinterface subsequent to the mapping, uplink user plane data of thequality of service flow to a data network via an N6 interface.
 15. Anon-transitory computer-readable storage medium storing instructionsexecutable by a processor of a network device, which when executed causethe network device to: receive a message pertaining to an establishmentof packet data unit (PDU) session for an end device, wherein the messageincludes a first message from a session management function and a secondmessage from a central unit-control plane function; determine that themessage includes collocation guidance information; select, in responseto the determination, a user plane function and a central unit-userplane function of the network device; and map, by the user planefunction and the central unit-user plane function, a quality of serviceflow to the PDU session directly with a radio bearer without anintermediary mapping of a General Packet Radio Service TunnelingProtocol User Plane (GTP-U) tunnel, wherein the quality of service flowincludes at least one of uplink or downlink user plane data.
 16. Thenon-transitory computer-readable storage medium of claim 15, wherein thenetwork device is of a fifth generation wireless network.
 17. Thenon-transitory computer-readable storage medium of claim 15, wherein theinstructions to map further comprise instructions, which when executedcause the network device to: map the quality of service flow between aPDU layer and a Service Data Adaptation Protocol (SDAP) layer.
 18. Amethod comprising: receiving, by a network device, a message pertainingto an establishment of packet data unit (PDU) session for an end device,wherein the first message includes data indicating a selection of theuser plane function and the second message includes data indicating aselection of the central unit-user plane function; determining, by thenetwork device, that the message includes collocation guidanceinformation; selecting, by the network device in response to thedetermining, a user plane function and a central unit-user planefunction of the network device; and mapping, by the user plane functionand the central unit-user plane function, a quality of service flow tothe PDU session directly with a radio bearer without an intermediarymapping of a General Packet Radio Service Tunneling Protocol User Plane(GTP-U) tunnel, wherein the quality of service flow includes at leastone of uplink or downlink user plane data.
 19. The method of claim 18,further comprising: transmitting, by the network device subsequent tothe mapping, downlink user plane data of the quality of service flow toa distributed unit-user plane function via an F1-U interface.
 20. Themethod of claim 18, further comprising: transmitting, by the networkdevice subsequent to the mapping, uplink user plane data of the qualityof service flow to a data network via an N6 interface.